Exploratory Testing (ET):
   Explore OR understand the application first, write the test cases and then test the application is k.a., ET.


Q: When to go for ET?
1. When reqts are not clear OR not updated
2. Reqts are present but no time to go through it.
3. The old application came for updation.
4. When you join the organization in the middle of the project.


Q: Dis-Advantages of ET?
1. There is no baseline to test the application.
2. We may understand feature as a defect.
3. We may understand defect as a feature.
4. If dev fails to implement any feature, QA will never come to know about it.
5. More rework both at Dev & QA side.
6. Wastage of time in exploring the root cause of the defects.
7. We may miss to find some defects.



Q: How to perform ET?
Ans:
   To perform ET, we need to follow "Exploratory Testing life cycle".

   
Exploratory Testing Life Cycle:

1. Identify the need for ET
          |
          V
2. Explore OR understand the application to the fullest
          |
          V
3. Write Test cases based on your understanding
          |
          V
4. Test case Review process **
   (a) Internal Review (Done by BA, Dev & Peer)
   (b) External Review (Done by Customer)
          |
          V
5. Fix all the review comments, baseline the testcases and store the test cases in test case repository
Ex: ALM, JIRA, SpiraqTest, SharePoint, Dedicated server etc
          |
          V
6. Select & execute the testcases based on the relase note scope whenever build comes. During test case execution If you find any defects it should be logged against dev in a defect tracking tool.
          |
          V
7. Prepare consolidate test execution report & attach all the test cases which QA has used to perform the testing.
Note: Attaching test cases is very important here. Also mention that the application is tested using only these attached test cases.



Q: How to make ET very effective?
Ans:
1. Explore the application to the fullest.
2. Effective interaction with BA.
3. Effective interaction with Dev.
4. Effective interaction with Customer.
5. Use your previous domain experience.
6. Proper documentation both at Dev & QA level.
7. Effective & timely review process at every steps.
**8. Use common sense